Adding new wave of plugins from chatgpt apps#154
Conversation
There was a problem hiding this comment.
per slack convo, will fast follow when we have the new hi-res assets.
There was a problem hiding this comment.
per slack convo, will fast follow when we have the new hi-res assets.
There was a problem hiding this comment.
per slack convo, will fast follow when we have the new hi-res assets.
There was a problem hiding this comment.
per slack convo, will fast follow when we have the new hi-res assets.
There was a problem hiding this comment.
per slack convo, will fast follow when we have the new hi-res assets.
…s-pr-122 # Conflicts: # .agents/plugins/marketplace.json
| "category": "Productivity" | ||
| }, | ||
| { | ||
| "name": "gitlab-issues", |
There was a problem hiding this comment.
hmm why's the name gitlab-issues and not gitlab?
There was a problem hiding this comment.
The ChatGPT app is called gitlab issues
| "category": "Coding" | ||
| }, | ||
| { | ||
| "name": "hubspot", |
There was a problem hiding this comment.
is this based on 1p or 3p app?
There was a problem hiding this comment.
3p hubspot app
## Summary This change removes the `gitlab-issues` plugin that was introduced in #154 from the local plugin marketplace and deletes the plugin bundle itself. The issue for users is straightforward: once the plugin is listed in the marketplace, it appears as an installable option in Codex. If that plugin should not be available, users can discover and attempt to use a connector that we do not want to ship from this repository. The root cause was the bulk plugin import in #154, which added `gitlab-issues` both to `.agents/plugins/marketplace.json` and to `plugins/gitlab-issues/`. That made the plugin available alongside the rest of that import wave. The fix removes the marketplace entry and deletes the plugin files so the repository state no longer advertises or ships `gitlab-issues`. ## Validation I validated the change by checking that `.agents/plugins/marketplace.json` still parses with `jq empty` and by running `git diff --check` to confirm the patch is structurally clean.
No description provided.